Storage system having a plurality of interfaces

ABSTRACT

A hybrid-type storage system having both SAN and NAS interfaces can be implemented by simple hardware capable of carrying out a SAN function independently of a NAS function and a NAS load. To be more specific, a controller of the storage system comprises a NAS controller for accepting an I/O command issued for a file unit and a SAN controller for accepting an I/O command issued for a block unit. The NAS controller converts an I/O command issued for a file unit into an I/O command issued for a block unit, and transfers the I/O command issued for a block unit to the SAN controller. The SAN controller makes an access to data stored in a disk apparatus in accordance with an I/O command received from the SAN or from the NAS controller as a command issued for a block unit. The NAS and SAN controllers are capable of operating independently of each other.

This application is a continuation of U.S. patent application Ser. No.11/517,387, filed Sep. 8, 2006, now U.S. Pat. No. 7,191,287, which is acontinuation of U.S. patent application Ser. No. 11/272,730, filed Nov.15, 2005, now U.S. Pat. No. 7,120,742, which is a continuation of U.S.application Ser. No. 10/805,260, filed Mar. 22, 2004, now U.S. Pat. No.6,981,094, which are incorporated by reference herein in their entirety.

BACKGROUND OF THE INVENTION

The present invention relates to a storage system having a plurality ofinterfaces. More specifically, the present invention relates to ahybrid-type storage system allowing accesses to data to be made by botha SAN (Storage Area Network)-interface command and a NAS (NetworkAttached Storage)-interface command.

In recent years, accompanying the growth of the application field of theinformation system and the progress of the distribution of processing ofa computer system, the number of hosts controlled at one site increasessubstantially. With the number of such hosts increasing, a problem of anincreased cost of managing storage systems is raised. In particular, ifstorage systems of distributed hosts are managed individually, thecapacity required by each storage system as a capacity necessary forcarrying out operations is difficult to estimate in advance. Thus, ifthere is a need to increase the capacity, it is necessary to newlyinstall an additional storage system for each individual host. Inconsequence, the management cost increases.

As technologies for solving the above problem, SAN and NAS techniquesare used. It is an object of both the technologies to consolidatestorage systems owned individually by distributed hosts. Due todifferent characteristics of the technologies, however, they are appliedto different fields.

The SAN technology is a technology for connecting a plurality of storagesystems and a plurality of hosts to each other by using a networkdedicated for communications between the hosts and the storage systemsin order to implement I/O operations having a high speed and a smalllatency. In accordance with the SAN technology, an I/O operation betweena host and a storage system is carried out in block units. A block is afixed-length data management unit identified by an address. A block isobtained as a result of dividing the capacity of a storage system intosmaller portions each having a predetermined size corresponding to thefixed length. A database is a representative of applications for whichthe I/O operation carried out in block units is suitable. Byconsolidating a plurality of database volumes into a single storagesystem so as to allow their management to be executed in a uniformmanner, the management cost of the computer system can be reduced. Inaddition, the SAN technology provides a dedicated network having highreliability and allows communications to be carried out with a highdegree of efficiency. Thus, the SAN technology can also be used as atechnique providing an effective communication path for transmittingdata in volume units. The transmission of data in volume units iscarried out to copy a volume to a remote storage system for the purposeof making a backup for the volume and for the purpose of providing acountermeasure to against accidents on the volume.

On the other hand, the NAS technology is a technique providing a storagesystem having a file-server function for rendering file services to aplurality of hosts existing in a LAN (Local Area Network). I/Ooperations between the storage system provided by the NAS technology andthe hosts are carried out in file units. In general, a file isidentified by using an identifier, which is a character string. A fileis a data management unit having a variable length. A representative ofapplications for which I/O operations carried out in file units aresuitable is an application of allowing a plurality of hosts to share afile. By adopting the NAS technology, it is possible to implement asystem allowing a plurality of web servers to share a service of thesame content and a system allowing a plurality of office PCs to share atext. As is obvious from the above description, the SAN and the NAStechnologies are mutually complementary. These technologies have led toformation of an idea of further reducing the management cost byintegration of storage systems conforming to the SAN with the NAStechnologies into a single storage system. In accordance withtechnologies disclosed in non-patent reference 1 and patent reference 1,which are described below, by providing a control program of a storagesystem as a control program allowing control of both the SAN and the NASstorage systems to be executed, a storage system conforming to both theSAN and the NAS technologies can be implemented. A storage systemapplying these technologies has SAN and NAS interfaces and allows astorage capacity thereof to be apportioned to the SAN and the NASinterfaces with a high degree of freedom.

It is to be noted that aforementioned patent reference 1 is JapanesePatent Laid-open No. 2003-162439. On the other hand, non-patentreference 1 cited above is a reference authored by Stephen Daniel with atitle of “Converging SAN and NAS Storage—A Comparison of Unified andGateway Solutions,” Network Appliance Inc., White Paper, October 2002.

SUMMARY OF THE INVENTION

In accordance with the technology disclosed in non-patent reference 1,it is possible to conform to the SAN and the NAS technologies by usingonly a single storage system. Since the SAN and the NAS technologies areimplemented by using a single control program, however, their functionsinterfere with each other, raising a problem. It is quite within thebounds of possibility that the SAN function is stopped due to a failureof the NAS function, causing a problem in a failure-proofcharacteristic. In addition, a maintenance work cannot be carried out bystopping only the NAS function. On the top of that, as the load of theSAN function becomes heavier, the performance of the NAS functiondeteriorates substantially. Likewise, if the load of the NAS functionbecomes heavier, on the other hand, the performance of the SAN functiondeteriorates substantially. Such phenomena make the performance designof the system as a whole difficult. In general, the SAN function servesas the mainstay of the storage system in many cases. Thus, there is ademand for a storage system, which allows operations to make accesses todata stored in a storage system to be continued by using the SANfunction even if the NAS function is stopped.

In accordance with the technology disclosed in patent reference 1, onthe other hand, the NAS and SAN functions are made more independent ofeach other so that it is possible to implement a storage system in whichthe SAN function is not stopped by a failure of the NAS function. Sincea plurality of interfaces having the NAS and SAN functions each controla disk apparatus of the storage system, however, hardware that mustcommunicate with an internal network through a shared memory becomesexpensive. Thus, it is difficult to apply this technology to a storagesystem with a small-scale configuration having a small number ofinterfaces.

It is thus an object of the present invention addressing the problemsdescribed above to provide a hybrid-type storage system having both SANand NAS interfaces as a storage system that can be implemented by simplehardware and is capable of operating as a SAN function without regard toNAS-related factors such as a failure of a NAS function and a NAS load.

The present invention thus provides a storage system allowing accessesto data stored in the storage apparatus thereof to be made through a SANinterface by using an I/O command issued for a block unit and a NASinterface by using an I/O command issued for a file unit. In thisstorage-system, a control unit for controlling the disk apparatuscomprises a NAS controller and SAN controller. The NAS controller is acontroller for receiving an I/O command issued for a file unit. On theother hand, the SAN controller is a controller for receiving an I/Ocommand issued for a block unit as a command to eventually make anaccess to data stored in the disk apparatus employed in the storagesystem.

The NAS controller converts a received I/O command issued for a fileunit into an I/O command issued for a block unit and supplies theblock-unit I/O command obtained as a result of the command conversion tothe SAN controller.

The SAN controller makes an access to data stored in the disk apparatusin accordance with a command received from the SAN interface as an I/Ocommand issued for a block unit or a command received from the NAScontroller as a block-unit I/O command resulting from the commandconversion.

As a result, the hybrid-type storage system having both SAN and NASinterfaces can be implemented by simple hardware and is capable ofoperating as a SAN function without regard to NAS-related factors suchas a failure of a NAS function and a NAS load.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing the configuration of a computer systememploying a storage system implemented by a first embodiment;

FIG. 2 is a block diagram showing typical configurations of NAS and SANcontrollers;

FIG. 3 shows a flowchart representing a typical command conversionprocess;

FIG. 4 is a diagram showing a typical data structure of a command queue;

FIG. 5 is a diagram showing another typical data structure of thecommand queue;

FIG. 6 shows flowcharts representing typical processes carried out atthe activation of a command conversion program, a disk-array controlprogram and a NAS-controller management program, which are provided bythe first embodiment;

FIG. 7 shows a flowchart representing a typical process, which iscarried out when the disk-array control program stops a NAS controller;

FIG. 8 shows flowcharts representing a typical process of a NAS plannedtermination subroutine called from the process represented by thesubroutine shown in FIG. 7;

FIG. 9 shows flowcharts representing a typical process of a NAS forcibletermination subroutine called from the process represented by thesubroutine shown in FIG. 7;

FIG. 10 is a block diagram showing a typical configuration of SAN/NAScontrollers; and

FIG. 11 shows flowcharts representing typical processes carried out atthe activation of a command conversion program and a disk-array controlprogram, which are provided by a second embodiment.

EMBODIMENTS OF THE INVENTION

Preferred embodiments of the present invention are explained byreferring to FIGS. 1 to 11 below. It is to be noted, however, that thescope of the present invention is not limited to these preferredembodiments described as follows.

First Embodiment

A first embodiment of the present invention is explained by referring toFIGS. 1 to 9 as follows.

First of all, by referring to FIG. 1, the following description explainsa typical configuration of a computer system employing a storage system100 implemented by the first embodiment of the present invention.

The storage system 100 implemented by the first embodiment is connectedto a plurality of computers each referred to as a SAN client 30 by a SAN50 composed of a fibre channel so that the storage system 100 is capableof receiving an I/O command from a SAN client 30. In addition, thestorage system 100 is also connected to a plurality of computers eachreferred to as a NAS client 20 by a LAN 40 so that the storage system100 is capable of receiving an I/O command from a NAS client 20. Insteadof being composed of a fibre channel, the SAN 50 may also be an IPnetwork for which an iSCSI protocol can be used.

The storage system 100 comprises a disk apparatus 105 and a controller110. The disk apparatus 105 referred also hereafter as a disk array 105comprises a plurality of disk drives 150 and a communication path 155for connecting the disk drives 150 to the controller 110.

The controller 110 is capable of inputting and outputting data from andto any of the disk drives 150 through the communication path 155. It isalso possible to provide a configuration in which the disk drives 150and the communication path 155 are included in the controller 110. Inaddition, the storage system 100 can also have a configuration includinga plurality of disk apparatus 105.

A SAN controller 140 is the main configuration component of thecontroller 110. A NAS controller 145 is implemented as a daughter boardmounted on the SAN controller 140. The controller 110 can also have aconfiguration including two SAN controllers 140 serving as working andspare controllers respectively. This configuration provides redundancyfor the purpose of improving reliability. To put it concretely, thespare SAN controller 140 is capable of functioning as a substitute forthe working SAN controller 140 to continue the function of the workingSAN controller 140 should a failure occur in the working SAN controller140.

Portions of the storage areas of the disk drives 150 are collected andgrouped to form a logical storage area, to which a continuous addressspace is assigned. Such a logical storage area is referred to as alogical volume. An I/O command issued for a block unit identified by anaddress in the address space assigned to the logical volume is referredto as a logical block access command. On the other hand, an I/O commandissued for a block unit identified by an address in an address spacepeculiar to a disk drive 150 is referred to as a physical block accesscommand.

The SAN controller 140 is connected to the disk apparatus 105, amanagement terminal 60 and the SAN 50. The SAN controller 140 has afunction to supply a physical block access command to one of disk drives150 in the disk apparatus 105 in accordance with a logical block accesscommand received from a SAN client 30.

Connected to the LAN 40, the NAS controller 145 can be plugged onto orremoved out off a connector 160 provided on the SAN controller 140. TheNAS controller 145 has a function to receive an I/O command issued for afile unit from a NAS client 20, convert the I/O command into a logicalblock access command and supply the logical block access command to theSAN controller 140. An I/O command issued for a file unit is referred tohereafter as a file command.

The SAN controller 140 manages configuration information 165 prescribinga relation between the disk drives 150 and logical volumes. Thecapability of managing the configuration information 165 allows the diskdrives 150 to be allocated as a NAS area 170 and a SAN area 175 with ahigh degree of freedom. The NAS area 170 is an area that can be used bythe NAS controller 145. On the other hand, the SAN area 175 is an areathat can be used by a SAN client 30. It is also possible to provide aconfiguration in which the NAS controller 145 and the SAN controller 140are implemented as a single board as is the case with a secondembodiment to be described later.

Connected to the SAN controller 140 and the NAS controller 145 by usinga network such as a LAN, the management terminal 60 comprises a screen,a keyboard and a mouse, which are operated to execute management of thestorage system 100. Management operations include activating andstopping the storage system 100, activating and stopping the NAScontroller 145, alteration of setting of the storage system 100including the SAN controller 140 and the NAS controller 145 andreference to information on a failure.

Next, the configurations of the SAN controller 140 and the NAScontroller 145 are explained by referring to FIG. 2. FIG. 2 is a blockdiagram showing typical configurations of the SAN controller 140 and theNAS controller 145.

A SAN processor 1409 on the SAN controller 140 is a processor for mainlyinterpreting and executing a disk-array control program 1405 and aNAS-controller management program 1406. The SAN processor 1409 uses aSAN memory 1407, which is connected to a SAN memory controller 1410, asa temporary storage device. The disk-array control program 1405 loadedin the SAN memory 1407 has a function to control a disk controller 1403by decoding a logical block access command received by a fibre-channelcontroller 1401 and converting the logical block access command into aphysical block access command. The disk-array control program 1405 takesadvantage of a disk cache 1402 to increase the speed to generate aresponse to a logical block access command.

On the other hand, the NAS-controller management program 1406 has afunction to activate and stop the NAS controller 145 and to refer toinformation on a failure in accordance with a management operationcarried out on the management terminal 60. The disk-array controlprogram 1405 and the NAS-controller management program 1406 are executedby the SAN processor 1409.

A NAS processor 1457 on the NAS controller 145 is a processor for mainlyinterpreting and executing a command conversion program 1453. The NASprocessor 1457 uses a NAS memory 1452, which is connected to a NASmemory controller 1456, as a temporary storage device. The commandconversion program 1453 loaded in the NAS memory 1452 has a function todecode a file command received by a LAN controller 1451 and convert thefile command into a logical block access command. The command conversionprogram 1453 supplies the logical block access command obtained as aresult of the conversion to the SAN processor 1409.

The disk-array control program 1405 executed by the SAN processor 1409has a function to convert a logical block access command received fromthe NAS controller 145 into a physical block access command. Thisconversion is identical with the process to convert a logical blockaccess command received from a fibre-channel controller 1401 into aphysical block access command as described above.

In an operation to transfer a logical block access command from the NASprocessor 1457 to the SAN processor 1409, the command conversion program1453 controls an inter-processor communication controller 1408. To putit in detail, a logical block access command is originally stored in aNAS communication-use area 1455 employed in the NAS controller 145.Controlled by the command conversion program 1453, the inter-processorcommunication controller 1408 typically carries out a DMA operation totransfer the logical block access command from the NAS communication-usearea 1455 to a SAN communication-use area 1404. On the other hand,status indicating a result of the execution of a command is reverselytransferred from the SAN communication-use area 1404 to the NAScommunication-use area 1455 upon completion of the execution of thecommand. If the inter-processor communication controller 1408 isprovided with an interrupt function for interrupting processes beingcarried out by the SAN processor 1409 and the NAS processor 1457,completion of a transfer of a command or status can be reported to theSAN processor 1409 and the NAS processor 1457 immediately.

If a file command received from a NAS client 20 is a command making arequest to write data into the storage system 100, the data istemporarily stored in a file cache 1454. Then, a logical block accesscommand obtained as a result of a conversion of the file command inaccordance with the procedure described above is transferred to the SANcommunication-use area 1404. Subsequently, the disk-array controlprogram 1405 transfers the data stored in a file cache 1454 to the diskcache 1402 in accordance with the logical block access commandtransferred to the SAN communication-use area 1404.

If a file command received from a NAS client 20 is a command making arequest to read out data from the storage system 100, on the other hand,a logical block access command obtained as a result of a conversion ofthe file command in accordance with the procedure described above istransferred to the SAN communication-use area 1404. Subsequently, thedisk-array control program 1405 reads out the data from a disk drive150, storing the data in the disk cache 1402. Finally, the disk-arraycontrol program 1405 transfers the data stored in the disk cache 1402 tothe file cache 1454 in accordance with the logical block access commandtransferred to the SAN communication-use area 1404.

A logical block access command and data can be exchanged between the NAScontroller 145 and the SAN controller 140 through a bus connected to theconnector 160 provided on the SAN controller 140 as a connector used formounting the NAS controller 145. In addition, the NAS controller 145 canbe plugged onto and removed out off the connector 160 while the SANcontroller 140 is operating. A PCI bus is a typical bus satisfying suchconditions. It is also possible to provide a configuration in which aplurality of NAS controllers 145 is mounted on the SAN controller 140.In such a configuration, as many inter-processor communicationcontrollers 1408 as the NAS controllers 145 are provided on the SANcontroller 140 as components for controlling communications between theSAN processor 1409 and the NAS controllers 145. In addition, it is alsopossible to provide a configuration in which the inter-processorcommunication controller 1408 is provided on the NAS controller 145.

As described above, the disk-array control program 1405 is a programhaving a function for converting a logical block access command into aphysical block access command. In this case, a logical block accesscommand is an I/O command received by the storage system 100 from a SANclient 30 by way of the SAN 50 as a command issued for a block unit in alogical volume logically defined as a volume logically comprising aplurality of disks in the disk array 105 of the storage system 100. Thelogical block access command can also be an I/O command received fromthe NAS controller 145 as a result of converting a file command. On theother hand, a physical block access command is an I/O command issued toa disk included in the logical volume as a disk corresponding to thelogical unit.

On the other hand, the command conversion program 1453 is a programhaving a function for converting an I/O command received by the storagesystem 100 from a NAS client 20 by way of the LAN 40 as a command issuedfor a file unit into an I/O command referred to as the logical blockaccess command issued for a block unit to be eventually converted by thedisk-array control program 1405 into an aforementioned physical blockaccess command as described above.

The disk-array control program 1405 operates independently of thefunction of command conversion program 1453. Thus, even if processingcarried out by the command conversion program 1453 can no longer becarried out because of a problem of the command conversion program 1453,the processing of the disk-array control program 1405 can be continuedto sustain a process carried out for an I/O command received from a SANclient 30.

Thus, a maintenance work can be carried out by stopping only the NASfunction. In addition, it is also possible to provide a configurationincluding a plurality of processors for executing the disk-array controlprogram 1405. By designating only some of the processors as processorsfor an I/O command transferred from the command conversion program 1453,the SAN performance can be sustained at least a predetermined level evenif the NAS load becomes heavier. Likewise, even if the SAN loadreversely becomes heavier, the NAS performance can be sustained at leasta predetermined level.

The command conversion program 1453 and the disk-array control program1405 for controlling the disk apparatus 105 communicate with each otherthrough an internal bus, requiring neither internal network nor sharedmemory. Thus, this configuration can be implemented at a low cost.

By referring to FIGS. 3 to 9, the following description explains controloperations carried out by the storage system 100 implemented by thefirst embodiment of the present invention.

With reference to a flowchart shown in FIG. 3, the description beginswith an explanation of processing operations, which are carried out bythe disk-array control program 1405 included in the configuration shownin FIG. 2 to catalog a command received from the command conversionprogram 1453 also included in the configuration shown in FIG. 2 or acommand received from the fibre-channel controller 1401 on a commandqueue.

FIG. 3 shows a flowchart representing a typical flow of a command fromthe command conversion program 1453 or the fibre-channel controller 1401to the command queue as a flow including a command conversion process.At a step 300, the command conversion program 1453 converts a filecommand into a logical block access command. Then, at the next step 302,the command conversion program 1453 transfers the logical block accesscommand to the SAN communication-use area 1404. Subsequently, at thenext step 305, a bit of a register of the inter-processor communicationcontroller 1408 is set to generate an interrupt. In the mean time, thedisk-array control program 1405 is in state of waiting for a logicalblock access command at a step 310. Interrupted by the inter-processorcommunication controller 1408, the disk-array control program 1405executes a step 315 to determine whether or not the command queue isbusy. If the command queue is not busy, the flow continues to a step 320to transfer the logical block access command from the SANcommunication-use area 1404 to the command queue. If the command queueis busy, on the other hand, the disk-array control program 1405 remainsin the waiting state till the command queue becomes no longer busy. Thecommand queue is busy because a logical block access command received bythe fibre-channel controller 1401 is being transferred to the commandqueue following an interrupt output by the fibre-channel controller 1401to the SAN processor 1409 or a logical block access command stored inthe SAN communication-use area 1404 is being transferred to the commandqueue as described above. Thus, the determination process of the step315 is a kind of exclusion control to prevent a logical block accesscommand stored in the SAN communication-use area 1404 from beingtransferred by the command conversion program 1453 to the command queuewhile a logical block access command is being transferred from thefibre-channel controller 1401 to the queue, and prevent a logical blockaccess command received by the fibre-channel controller 1401 from beingtransferred to the command queue while a logical block access command isbeing transferred by the command conversion program 1453 from the SANcommunication-use area 1404 to the queue. The exclusion control istypically implemented by assigning an equal priority level to interruptsoutput by the inter-processor communication controller 1408 and thefibre-channel controller 1401 to the SAN processor 1409 and carrying outthe operation to transfer a logical block access command from the SANcommunication-use area 1404 or the fibre-channel controller 1401 to thecommand queue as a process for handling an interrupt.

Typical data structures of the command queue are explained by referringto FIGS. 4 and 5. FIGS. 4 and 5 are diagrams each showing a typical datastructure of the command queue.

The command-queue data structures shown in the diagrams each includeboth logical block access commands transferred from the SANcommunication-use area 1404 and logical block access commandstransferred from the fibre-channel controller 1401. As describedearlier, the logical block access commands transferred from the SANcommunication-use area 1404 are each a result of a command conversionprocess carried out by the command conversion program 1453 included inthe configuration shown in FIG. 2.

In the typical data structure shown in FIG. 4, a command-queue-headpointer 400 points to the address of a logical block access command tobe executed next. On the other hand, a command-queue-tail pointer 410points to the address of a logical block access command newly added tothe tail of the command queue. In the data structure, NAS commands 415are each a logical block access command transferred from the SANcommunication-use area 1404 as a result of a command conversion processcarried out by the command conversion program 1453 while SAN commands420 coexisting with the NAS commands 415 are each a logical block accesscommand transferred from the fibre-channel controller 1401. The logicalblock access commands cataloged on the command queue are processedsequentially on a FIFO (First. In First Out) basis.

It is to be noted that the command queue is stored in the SAN memory1407 included in the configuration shown in FIG. 2.

The typical data structure shown in FIG. 5 is different from the typicaldata structure shown in FIG. 4 in that, in the case of the datastructure shown in FIG. 5, the logical block access commands arecataloged in separate queues, i.e., a NAS queue used for cataloging NAScommands 515 and a SAN queue used for cataloging SAN commands 565.

A logical block access command stored in the SAN communication-use area1404 as a result of a command conversion process carried out by thecommand conversion program 1453 is transferred to a NAS-queue locationpointed to by a NAS command-queue-tail pointer 510. On the other hand, alogical block access command received from the fibre-channel controller1401 is transferred to a SAN-queue location pointed to by a SANcommand-queue-tail pointer 560.

The command-queue data structure shown in FIG. 5 is characterized inthat control can be executed to determine whether processing of a NAScommand takes precedence of processing of a SAN command, or theprocessing of a SAN command takes precedence of the processing of a NAScommand. That is to say, in order to process an I/O request made by aNAS client 20 shown in FIG. 1, taking precedence of an I/O request madeby a SAN client 30 shown in the same figure, a NAS command pointed to bya NAS command-queue-head pointer 500 is executed first. In order toprocess an I/O request made by a SAN client 30 by taking precedence ofan I/O request made by a NAS client 20, on the other hand, a SAN commandpointed to by a SAN command-queue-head pointer 550 is executed first.

By referring to flowcharts shown in FIG. 6, the following descriptionexplains processing of the activation of the command conversion program1453, the disk-array control program 1405 and the NAS-controllermanagement program 1406 which are provided by the first embodiment. FIG.6 shows flowcharts representing typical processes carried out at theactivation of the command conversion program 1453, the disk-arraycontrol program 1405 and the NAS-controller management program 1406.

When the power supply of the storage system 100 shown in FIG. 1 isturned on, the SAN controller 140 and the NAS controller 145 areinitialized. After the SAN controller 140 is initialized, an IPL loadsthe disk-array control program 1405 and the NAS-controller managementprogram 1406 from a disk drive 150 into the SAN memory 1407 included inthe configuration shown in FIG. 2. Then, the SAN processor 1409 startsexecuting the disk-array control program 1405 and the NAS-controllermanagement program 1406. The NAS-controller management program 1406enters a wait state at a step 635.

After the NAS controller 145 is initialized, an IPL loads an activationroutine of the command conversion program 1453 from a ROM mounted on theNAS controller 145. Since the command conversion program 1453 wasinstalled in a disk drive 150, this IPL cannot load the commandconversion program 1453 because the IPL cannot make an access to anydisk drive 150. For this reason, the IPL loads the activation routine ofthe command conversion program 1453 first. The activation routine entersa state of waiting for a notice indicating completion of aninitialization of the disk array 105 at a step 600.

In the mean time, the started disk-array control program 1405initializes the disk array 105 at a step 625. After, the initializationof the disk array 105 is completed, the disk-array control program 1405transmits a notice indicating the completion of the initialization ofthe disk array 105 to the activation routine at the next step 630.

Receiving the notice indicating the completion of the initialization ofthe disk array 105, the activation routine initializes the NAS memory1452 at a step 605. Then, at the next step 610, the activation routineinforms the NAS-controller management program 1406 that the NAS memory1452 has been initialized. Subsequently, at the next step 615, theactivation routine enters a state of waiting for a notice to be given bythe NAS-controller management program 1406. Informed of the fact thatthe NAS memory 1452 has been initialized at the step 635, theNAS-controller management program 1406 loads the command conversionprogram 1453 from a disk drive 150 into the NAS memory 1452 at a step640 by using a means such as the DMA technique.

At the next step 645, the NAS-controller management program 1406notifies the activation routine of the command conversion program 1453that the operation to load the command conversion program 1453 has beencompleted.

Notified of the fact that the operation to load the command conversionprogram 1453 has been completed at the step 615, the activation routineof the command conversion program 1453 executes a jump to the entrypoint of the command conversion program 1453 at the next step 620. Inthis way, the execution of the command conversion program 1453 isstarted.

By referring to flowcharts shown in FIGS. 7 to 9, the followingdescription explains processing carried out by the disk-array controlprogram 1405 to stop the NAS controller 145. FIG. 7 shows a flowchartrepresenting a typical process, which is carried out when the disk-arraycontrol program 1405 stops the NAS controller 145. FIG. 8 showsflowcharts representing a typical process of a NAS planned terminationsubroutine called from the process represented by the subroutine shownin FIG. 7. FIG. 9 shows flowcharts representing a typical process of aNAS forcible termination subroutine called from the process representedby the subroutine shown in FIG. 7.

At a step 705 of the flowchart shown in FIG. 7, a stop command to haltthe NAS controller 145 is received from the management terminal 60 whilethe disk-array control program 1405 is processing a SAN or NAS commandat a step 700. In this case, the flow of the process goes on to a step710 at which a NAS planned termination process is carried out. Detailsof the NAS planned termination process will be explained later.

If no command to stop the NAS controller 145 is received from themanagement terminal 60 at the step 705, on the other hand, the flow ofthe process goes on to a step 725 to determine whether or not a timeoutof a heartbeat signal received from the command conversion program 1453at predetermined intervals has occurred. The occurrence of such atimeout can be interpreted as detection of an abnormality of the NAScontroller 145. If an abnormality has been detected, the flow of theprocess goes on to a step 730 at which NAS commands are discarded fromthe command queue. Then, at the next step 735, a NAS forcibletermination process is carried out. Details of the NAS forcibletermination process will also be explained later. After the execution ofthe NAS planned termination process or the NAS forcible terminationprocess is completed, the flow of the process goes on to a step 712 totransit to a SAN operation mode of processing only SAN commands.

When the operation of the NAS controller 145 is resumed in accordancewith a resume command received from the management terminal 60, thestorage system 100 transits to a SAN/NAS operation mode beginning at thestep 700 at which the disk-array control program 1405 processes a SAN orNAS command. The NAS controller 145 can be resumed by having thedisk-array control program 1405 return control to the step 630 of theflowchart shown in FIG. 6.

At a step 800 of the NAS planned termination process represented by theflowcharts shown in FIG. 8, the NAS-controller management program 1406gives a notice of a planned termination to the command conversionprogram 1453. After receiving the notice of a planned termination at astep 815, the command conversion program 1453 transfers written datastored in the file cache 1454 to a disk cache 1402 at the next step 820.Then, at the next step 825, the command conversion program 1453 gives anotice of completion of the planned termination to the NAS-controllermanagement program 1406.

After receiving the notice of completion of the planned termination at astep 805, the NAS-controller management program 1406 records thetermination of the NAS controller 145 at the next step 810. Thereafter,the NAS controller 145 is not monitored anymore.

At a step 905 of the NAS forcible termination process represented by theflowcharts shown in FIG. 9, the command conversion program 1453 is putin a hung-up state caused by a generated failure, entering an endlessloop at the next step 910. In this endless loop, the command conversionprogram 1453 is not capable of carrying out communications at all. Inthe mean time, the NAS-controller management program 1406 gives a noticeof a forcible termination of the command conversion program 1453 to theNAS processor 1457 by using a hardware means such as a terminationsignal at a step 900. The notice of a forcible termination of thecommand conversion program 1453 causes the NAS controller 145 to enter astate in which the SAN controller 140 is not affected and data is notdestroyed even if the power supply of the NAS controller 145 is cut off.Thus, a repair work such as replacement of the NAS controller 145 can becarried out.

This embodiment has a configuration in which the operation of the SANcontroller 140 serving as hardware with the SAN function is notdependent on the operation of the NAS controller 145 serving as hardwarewith the NAS function. Thus, the operation of the SAN function can becontinued in the event of a failure of the NAS function without beingaffected by the failure. Examples of the failure of the NAS functioninclude a hardware failure of the NAS controller 145 and a softwarefailure of the command conversion program 1453. In addition, amaintenance work can be carried out by carrying out a plannedtermination of the NAS function, which can be resumed later after thework. That is to say, the disk-array control program 1405 executed bythe SAN processor 1409 mounted on the SAN controller 140 is capable ofoperating to accept an I/O command received from the SAN 50 as a commandissued for a block unit. The disk-array control program 1405 is capableof processing such an I/O command independently of the existence of alogical block access command received from the NAS controller 145. Asdescribed earlier, the logical block access command received from theNAS controller 145 is a command obtained as a result of a conversionprocess of an I/O command, which is received by the NAS controller 145as a command issued for a file unit.

In addition, since neither an internal network nor a shared memory isrequired for communications between the NAS controller 145 and the SANcontroller 140, the storage system 100 can be implemented at a lowhardware cost. Furthermore, since the NAS controller 145 does notrequire a processor for executing the disk-array control program 1405,the NAS controller 145 can also be implemented at a low hardware cost aswell.

On the top of that, by separating the queue used for cataloging NAScommands 515 from the queue used for cataloging SAN commands 565 asshown in FIG. 5, a NAS command 515 can be processed, taking precedenceof SAN commands 565, or a SAN command 565 can be processed, takingprecedence of NAS commands 515.

Moreover, it is also possible to provide a configuration including 2 ormore pairs of the SAN processor 1409 and the SAN memory 1407, which areshown in the configuration of FIG. 2, on the same SAN controller 140. Insuch a configuration, a SAN processor 1409 for processing a NAS queuefor managing NAS commands 515 can be provided separately from a SANprocessor 1409 for processing a SAN queue for managing SAN commands 565and, in addition, the queue used for cataloging NAS commands 515 and thequeue used for cataloging SAN commands 565 can be stored in differentSAN memories 1407. In this configuration, a processing system processesI/O requests made by a NAS client 20 independently of processing carriedout by another processing system to process I/O requests made by a SANclient 30. Thus, even if the load borne by a particular one of theprocessing systems becomes heavier, the performance of the otherprocessing system can be assured without being affected by theparticular processing system. As a result, the performance of the systemas a whole can be contemplated with ease.

Second Embodiment

A second embodiment of the present invention is explained below byreferring to FIGS. 10 and 11. First of all, the second embodiment of thepresent invention is explained by referring to FIG. 10 as follows.

FIG. 10 is a block diagram showing a typical configuration of SAN/NAScontrollers. The second embodiment is obtained by replacing portionscorresponding to the SAN controller 140 and NAS controller 145 of thefirst embodiment shown in FIG. 1 with a SAN/NAS controller 1000 shown inFIG. 10.

Interfaces of the SAN/NAS controller 1000 with the LAN 40, the SAN 50,the management terminal 60 and the disk apparatus 105 are the same asthe interfaces of the SAN controller 140 and the NAS controller 145. Thesecond embodiment is different from the first embodiment in that, in thecase of the second embodiment, the SAN processor 1409 and the NASprocessor 1457 share a memory controller 1025 and a memory 1005. Thememory 1005 is divided into a NAS-processor-use area 1010 and aSAN-processor-use area 1015.

Executed by the NAS processor 1457, the command conversion program 1453has a function to interpret a file command received by the LANcontroller 1451 and convert the file command into a logical block accesscommand. The command conversion program 1453 supplies the logical blockaccess command resulting from the conversion to the SAN processor 1409.The command conversion program 1453 executed by the NAS processor 1457supplies the resulting logical block access command to the SAN processor1409 by way of a shared memory 1020, which is used by the SAN processor1409 and the NAS processor 1457 to exchange data with each other. Thedisk-array control program 1405 recognizes a logical block accesscommand supplied by the SAN processor 1409 by polling or a processorinterrupt, and converts the logical block access command into a physicalblock access command in the same way as the first embodiment.

Devices provided on the SAN/NAS controller 1000 as devices other thanthe memory controller 1025 and the memory 1005 are not shared by the SANprocessor 1409 and the NAS processor 1457. To be more specific, the SANprocessor 1409 exclusively uses the fibre-channel controller 1401, thedisk cache 1402 and the disk controller 1403. On the other hand, the NASprocessor 1457 exclusively uses the LAN controller 1451. A route in aninterrupt controller embedded in the memory controller 1025 is set toapply interrupts generated by devices exclusively used by the SANprocessor 1409 to the SAN processor 1409 and interrupts generated bydevices exclusively used by the NAS processor 1457 to the NAS processor1457.

By referring to flowcharts shown in FIG. 11, the following descriptionexplains activation processes of the command conversion program 1453 andthe disk-array control program 1405, which are executed in the secondembodiment of the present invention.

FIG. 11 shows the flowcharts representing typical processes carried outat the activation of the command conversion program 1453 and adisk-array control program 1405, which are provided by the secondembodiment of the present invention.

In this embodiment, since the SAN processor 1409 and the NAS processor1457 share the memory controller 1025, it is impossible to activate andstop only the command conversion program 1453 by using a hardware means.Thus, before the command conversion program 1453 is activated orreactivated, first of all, the NAS-controller management program 1406clears the contents of the NAS-processor-use area 1010 to all zeros at astep 1100. Then, at the next step 1105, the NAS-controller managementprogram 1406 copies data stored in a disk used by the command conversionprogram 1453 to the NAS-processor-use area 1010. Subsequently, at thenext step 1110, by using an interrupt, the NAS-controller managementprogram 1406 informs the NAS processor 1457 that the copy process hasbeen completed.

In the mean time, at a step 1115, the NAS processor 1457 is in a stateof waiting for an other-system activation command processor interrupt,which is peculiar to a multi-processor system. Receiving such aninterrupt, the NAS processor 1457 executes a jump to the entry point ofthe command conversion program 1453 at the next step 1120 to start theexecution of the program.

The second embodiment employs fewer components than the first embodimentso that the storage system 100 provided by the second embodiment can beimplemented at a lower cost. The first embodiment employs two or moresets of a memory controller and its peripheral circuit. On the otherhand, the second embodiment can live with only one set of a memorycontroller and its peripheral circuit. In addition, in the case of thesecond embodiment, the shared memory 1020 shared by the NAS processor1457 and the SAN processor 1409 is used for inter-processorcommunications. Thus, the hardware such as the inter-processorcommunication controller 1408 of the configuration shown in FIG. 2 isnot required. In the case of the second embodiment, however, the NAS-usehardware cannot be replaced while the SAN/NAS controller 1000 isoperating without affecting the operation of the SAN function.

1. A storage device receiving file and block I/O commands comprising: amemory storing a command conversion program and a disk array controlprogram; a NAS processor which executes said command conversion programfor converting file commands to logical block commands; a SAN processorwhich executes said disk array control program for converting saidlogical block commands to physical block commands, implemented on asingle board with said NAS processor; a memory controller coupled tosaid NAS processor and to said SAN processor and said memory; and a diskcontroller coupled to a plurality of disk drives.
 2. The storage deviceaccording to claim 1, further comprising: a LAN controller; and a fibrechannel controller; wherein said fibre channel controller and said diskcontroller are exclusively used by said SAN processor, and wherein saidLAN controller is exclusively used by said NAS processor.
 3. The storagedevice according to claim 1, wherein said memory includes a sharedportion for receiving and sending data between said NAS processor andsaid SAN processor, a NAS portion storing said command conversionprogram, and a SAN portion storing said disk array control program. 4.The storage device according to claim 3, further comprising: a pluralityof disk drives, wherein said SAN portion includes a NAS controllermanagement program, wherein in order to activate said command conversionprogram, said NAS controller management program clears contents storedin said NAS portion, reads out data used by said command conversionprogram from said disk drive and copies said data to said NAS portion,and informs completion of said copying to said NAS portion to said SANportion.
 5. The storage device according to claim 4, wherein during theactivation of said command conversion program said NAS processor waitsfor an other-system activation command processor interrupt, and executesa jump to the entry point of said command conversion program to start anexecution of said command conversion program.
 6. The storage deviceaccording to claim 1, wherein said memory includes a program to activatesaid command conversion program.
 7. The storage device according toclaim 6, wherein said NAS processor waits for an interrupt to activatesaid command conversion program.